Data Joins with dplyr
For this assignment, you’re going to re-create this .html file and
get to use some of the data joining functions from the
dplyr package.
You can review the slides for this assignment here, and the exercises are here
Step 1:
Create the project using the
goodenuffR::goodenuff_project() function:
goodenuffR::goodenuff_project(
project_name = "wk11-table-joins",
folder_path = "path/to/hw/folder")Replace path/to/hw/folder with the path to
your folder.
Step 2:
Install the following packages by running this in the Console
install.packages(c("tidyverse", "starwarsdb", "dm"))Install rmdformats package by running this in the
Console
install.packages(remotes) # if necessary
remotes::install_github("juba/rmdformats")Load rmdformats package by running this in the
Console
library(rmdformats)Step 3:
Create a new R Markdown file using FIle > New File > R Markdown… > From Template > Then give this file a name
Step 4:
Replace the setup chunk with the code below:
library(tidyverse)
library(starwarsdb)
library(dm)
# create data folder
knitr::opts_chunk$set(
cache = FALSE,
echo = TRUE,
collapse = FALSE,
eval = TRUE,
message = FALSE,
warning = FALSE,
dev = "ragg_png",
out.width = '85%',
fig.path = "img/",
dpi = 320,
fig.align = "center",
fig.width = 7,
fig.height = 5.5,
fig.retina = 2
)
# tibble printing
options(
pillar.print_max = 10,
pillar.print_min = 10)Step 5:
Create outline using Markdown syntax
# Objectives
## Load packages
## Toy data
# Joins
## `starwarsdb`
## Create `StarWarsFilms`
## `left_join` {.tabset}
### Example
### Solution
## `inner_join` {.tabset}
### Example
### Solution
## `right_join` {.tabset}
### Example
### Solution
## `anti_join` {.tabset}
### Example
### SolutionStep 6 Exercises:
Copy and paste the necessary sections from the exercises to get the Example and Solution to work
All of the exercises should have the code chunks set to
eval=TRUEYou can set the
setupchunk toerror=TRUE, so if a code chunk doesn’t render and look like the example in the exercises, read the error and try to de-bug (this is a huge part of coding)
Knit, and knit often:
- Every time you change an
evalargument, click on the “Knit” icon in R Studio and review the output. This will prevent errors from building up (and you get to see your handy work!)